docs(tools): guía actualizada de upscale, Revoice y quitar fondo - #225
docs(tools): guía actualizada de upscale, Revoice y quitar fondo#225cursor[bot] wants to merge 3 commits into
Conversation
Document the post-processing Tools panel (upscale, SeedVC revoice, rembg) against the current HTTP and worker contracts, including the unused instruction field and narrower rembg formats. Cross-link the HOWUSEIT index, README, API, and related guides; note local Music3 vs remote MiniMax and persist-before-generate song identity; record validate_local PATH inheritance and fail-closed UI steps. Co-authored-by: ignaciodelcano+dcl <ignaciodelcano+dcl@gmail.com>
PR Review — Loreframe StudioRisk: low Automated review from Findings
Changed files
CONTRIBUTING checklist
Posted by the repo PR review workflow. Re-runs on each push to the PR. |
Code healthQuality score: 58.7/100Higher is better. The score is a trend dashboard; the independent ratchet below remains the CI gate.
Change vs PR base: +0.0 points.
Markdown, JSON catalogs and tests are out of this table. Only Most complex functions
Trend vs baseline
Ratchet passed. |
|
Revisión independiente: sigue en draft. No retarget ni ready. La guía de Tools y la corrección de
Además, frente a Hay que reescribir esas afirmaciones (y mejor contra |
Resumen ejecutivo
Qué cambia
Añade una guía de Studio Tools y actualiza sus enlaces y documentación de API sobre la base actual de development.
Para qué sirve
Aclara qué camino usa cada operación: upscale por el comando compartido V2 desde Studio/Wizard/MCP; Revoice y quitar fondo por sus rutas nativas. Corrige afirmaciones obsoletas sobre Revoice en Wizard, referencias, métodos y selección de recursos.
Impacto para el usuario
Los ejemplos usan el contrato vigente. Se explica cómo conservar carpeta fuente, recibo e intención de una petición, y que las instrucciones de rembg son metadatos: no dirigen la máscara.
Riesgo
Estado
Summary
Refresh the proposed Tools operator guide against development, including shared
tools.upscaleV2 and its receipt/replay behavior. Keep the native legacy schemas distinct. Remove unrelated music and local-validation changes from this PR's final scope.Overview
Choose an existing source in Studio Tools, select the operation and parameters, then follow the returned job. The source remains intact and results belong to the destination output folder. The guide distinguishes that folder from a logical Workspace collection and preserves the source URL scope.
Detailed changes
Backend
No runtime changes. API documentation distinguishes the version 2 command envelope from flat native Tools requests, explains rembg's accepted formats and metadata-only instruction, and describes Revoice's one/two-reference behavior.
UI and Wizard
Document the current resource picker and processor discovery. Wizard has upscale and remove-background adapters; it does not expose a dedicated Revoice action. Do not infer shared support for all Tools from the existence of
tools.upscale.Data, provenance and compatibility
The shared upscale example requires a canonical resource or exact asset ID, explicit method/kind/output workspace and stable
intent_idfor response recovery. Native paths retain their existing separate contract. No persistence, model, launcher or runtime changes.Files and ownership
docs/tools/HOWUSEIT.md: operator guide and examples.app/docs/API.md: current HTTP contracts and shared-command links.README.md,docs/HOWUSEIT.md, Character Kits and Video Editor guides: Tools links only.Validation
73ec9091badd6e3e90c7bba70d5114a816c29ecc(development).978b7a92e46aacba79a1ff0d3627836c8293b564.original; the rembg example passes its actual request schema. Revoice JSON shape inspected against its native handler.git diff --check: PASS. No product or tests delta against development.CI and review
CI requiredSUCCESS. Both Cursor automations completed successfully; formal Independent QA remains NEUTRAL.Notes and limitations
This guide documents implemented behavior, not a new shared Revoice/rembg operation or a quality guarantee for every processor. Example resources must exist before executing the commands. The standalone link check verifies local file targets, not every fragment or external website.